Skip to content

Relocate unused GraphDB custom-rules example out of active config #11

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

trondaal
Copy link
Owner

Summary

  • database/inference_rules/inverse.rules.pie was sitting alongside live config (database/types/, database/lucene_connectors/), implying it was loaded by GraphDB. It wasn't — the active repository config in docker/graphdb/repositories/EntEdit/config.ttl sets graphdb:ruleset "rdfsplus-optimized" (a built-in ruleset) and never references the .pie file.
  • Moved it to docs/examples/graphdb-custom-rules/ with a short README explaining it's a reference example for authoring a custom PIE ruleset, and pointing at the GraphDB reasoning docs.
  • Removed the now-empty database/inference_rules/ directory and dropped the entry from the repository-structure trees in README.md, CLAUDE.md, and the English + Norwegian setup.html docs.
  • No GraphDB configuration or runtime behavior changes.

Test plan

  • Confirm database/inference_rules/ is gone and docs/examples/graphdb-custom-rules/ contains the .pie file plus README
  • Verify docker/graphdb/repositories/EntEdit/config.ttl is unchanged
  • Skim the rendered setup.html repo-structure tree (en + no) to confirm the listing reads cleanly

🤖 Generated with Claude Code

Move database/inference_rules/inverse.rules.pie to
docs/examples/graphdb-custom-rules/ and add a README explaining it's a
reference example, not live config. The running stack uses the built-in
rdfsplus-optimized ruleset (docker/graphdb/repositories/EntEdit/config.ttl)
and never loaded the .pie file, so its placement under database/ alongside
types/ and lucene_connectors/ falsely implied it was wired in.

Also update README.md, CLAUDE.md, and the setup.html docs (en + no) to
drop the inference_rules/ entry from the repository-structure trees.

No GraphDB configuration or runtime behavior changes.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Sign in to join this conversation on GitHub.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant